Systems and methods for implementing an automated parallel deployment solution

ABSTRACT

Systems and methods are provided for implementing an automated parallel deployment solution. Embodiments of the invention described herein prevent defects from being introduced in a production environment, or those that could be introduced in a production environment, by parallel log monitoring of existing and new state systems. One or more systems may be created in parallel to the production system to detect and fix defects. In embodiments of the invention, as existing defects are captured and resolved by the automatic defect resolution system and method, these defects will not impact production any further. Thus, the automatic defect resolution system drives out all production defects over a window of time, requiring less and less maintenance over time. Once a given defect is fixed, the corresponding change is applied to the production environment to avoid future similar defects.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation of U.S. application Ser. No.15/460,263, filed Mar. 16, 2017, which is a Continuation of U.S.application Ser. No. 14/632,364, filed Feb. 26, 2015, now U.S. Pat. No.9,632,886, the disclosures of which, including the specification,drawings, and claims, are expressly incorporated herein by reference intheir entirely.

FIELD OF THE INVENTION

Embodiments of the invention relate generally to implementing a parallelvirtual production environment.

BACKGROUND

High volume distributed production systems with many points ofmodification are subject to frequent defects due to their complexity andthe complexity of managing these solutions. Previous solutions haveincluded attempts by companies to provide self-healing systems andredundant (“failover”) systems. However, these existing systems relyupon the failover system itself to be either completely unified underthe company's platform, or at the very least to be provided or hosted bythe company. Further, these existing systems are not expandable toincorporate new error scenarios, making them unadaptable. They alsocannot capture human expert solutions, and are extremely complicated toinstall and use.

A solution is needed in which an automatic defect resolution systemoperates independently of the environment and systems which itadministers and can be turned off and on without adversely impactingproduction running. An automatic defect resolution system that operatesby parallel log monitoring of existing and new state systems wouldresolve many of these problems.

Ideally, such systems would not require advanced technical knowledge toinstall, operate or maintain, making them extremely simple to installand use. More elegantly designed systems would avoid problems associatedwith currently existing high overhead/high architecture solutions, whichhave limited expandability into unknown errors. Human expert solutionscould be captured and expanded to capture any future error scenarios.Further, interval based transaction tolerances could be used tomathematically guarantee performance within intervals. Most of all, anideal solution would eliminate delays associated with promoting changesto the production system.

Accordingly, such an automated parallel deployment system would resolvemany of the shortcomings currently present in existing defect solutions.

SUMMARY OF THE INVENTION

Embodiments of the invention are directed to a system comprising: amodeling module for modeling a parallel system solution generated inresponse to a system request and creating a record of the parallelsystem solution; a production module for modeling a production systemsolution generated in response to the system request and creating arecord of the production system solution; a processor for comparing therecord of the parallel system solution and the record of the productionsystem solution, and for further applying a series of interval-basedtransaction tolerances on the comparison; a solution module forfinalizing a functional solution; and a promotion module for promotingthe functional solution to a production system.

Embodiments of the invention are also directed toward a method forimplementing an automated parallel deployment solution, the methodcomprising: modeling a parallel system solution generated in response toa system request; creating a record of the parallel system solution;modeling a production system solution generated in response to thesystem request; creating a record of the production system solution;comparing the record of the parallel system solution and the record ofthe production system solution, applying a series of interval-basedtransaction tolerances on the comparison; using the compared transactionresults to reach a functional solution; and promoting the acceptablesolution to a production system.

Further embodiments of the invention are directed towards a system forimplementing an automated parallel deployment solution, the systemcomprising: a modeling module for modeling a parallel system solutiongenerated in response to a system request and creating a record of theparallel system solution; a production module for modeling a productionsystem solution generated in response to the system request and creatinga record of the production system solution; a processor for comparingthe record of the parallel system solution and the record of theproduction system solution, and for further applying a series ofinterval-based transaction tolerances on the comparison; a promotionmodule for promoting a functional solution to a production system; anautomatic issue resolution component associated with the productionsystem; and a defect repository for storing automated system solutions;wherein automated system solutions are stored in an automatic resolutiondefect repository and tested using interval-based transactiontolerances.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawings:

FIG. 1 is a flow chart illustrating an automated defect resolutionsystem with interval analysis in accordance with embodiments of theinvention;

FIG. 2 is a flow chart illustrating a parallel deployment with intervalanalysis system in accordance with embodiments of the invention;

FIG. 3 is a is a block diagram illustrating an operating environment fora system in accordance with embodiments of the invention;

FIG. 4 is a parallel system illustrated in accordance with embodimentsof the present invention; and

FIG. 5 is a parallel system illustrated in accordance with embodimentsof the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the invention relate to a technique for employing anautomatic defect resolution system, particularly within a productionenvironment.

As show in the data flow diagram of FIG. 1, the automated paralleldeployment system begins deployment with a request at S101. This requestmay be any type of request, such as, e.g., a request to scan anAutomated Teller Machine (ATM) receipt. The request notification at S102proceeds through production system at S103. A production file is thengenerated at S104 (which may also be referred to as a production log).In embodiments of the invention, a defect may present that preventsfurther processing of the request. Such a defect may be any type ofknown defects that may occur within a production system. For example, inthe example given above, in which the request at S101 is a request toscan an ATM receipt, the defect may be associated with a problem in therelevant database which is preventing the request from being processed.Once the defect has been detected, the system will first attempt anautomatic issue resolution at S105 by matching on known defect patterns.In embodiments of the invention, this process may resolve the defect andthe request initially made at S101 can continue to be processed.

In embodiments of the invention, however, the automatic issue resolutionat S105 may not match on known defect patterns. Accordingly, the systemmay then run an automated fix from a defect repository at S106. Once theautomated fix has been run, it may then be assessed by the systemwhether the automated fix will cause a tolerance issue at S107 throughthe deployment of interval-based transaction tolerances at S108. Suchinterval-based transaction tolerances may be designed and run accordingto known principles of interval analysis and proximate reasoning. Inembodiments of the invention, interval analysis will require and performa transformation on an upper bound and a lower bound for a range ofresults, allowing the system to determine whether, e.g., variations inthe system are anomalous and require further attention. In embodimentsof the issue, the interval analysis may show that the associated machineand/or hardware is producing the anomalous results. Running theinterval-based transaction tolerances also ensures any solutions runthrough the analysis will be accurate and suitable for production (thatis, not impacted by prior solutions and/or any other consequences ofrunning the interval analysis in the first instance). If no toleranceissue is detected through the deployment of an interval basedtransaction tolerances at S108, the defect may be closed as resolved atS109, and the initial request made at S101 can continue to be processedwithin the production system. If the automated fix run from thedepository at S106 does cause a tolerance issue at S107, a record of themanual fix for the tolerance issue will be generated and recorded atS110 in a repository at S111. Accordingly, the next time the same defectarises, the problem may be solved by automatic issue resolution bymatching on known defect patterns at S105.

In embodiments of the invention, the automatic issue resolution at S105may be performed and/or validated against systems and methods asdepicted in exemplary FIG. 2. In embodiments of the invention, theintegration of FIGS. 1 and 2 may allow for the system to be partly orcompletely automated. In embodiments of the invention, the system may,in response to a request made at S201, use a request duplicator at S202to duplicate the request made at S201 into Parallel System Request atS203 and Production System Request at S204. In response, Parallel SystemLogs at S205 and Production System Logs at S206 are generated. In thisway, one or more systems may be created in parallel to the productionsystem to detect and correct defects. The transaction results arecompared at S207 in order to determine whether the results are outsideof a previously determined range according to interval-based transactiontolerances at S208. As previously explained, these interval-basedtransaction tolerances, which may be designed and run according to knownprinciples of interval analysis, help to ensure that any solutions runthrough the analysis will be not be impacted by prior solutions and/orany other consequences of running the interval analysis in the firstinstance. As existing defects are captured and resolved by the automaticdefect resolution system and method, these defects will not impactproduction any further. Subsequently, the system will assess to seewhether an aberrant result was produced at S209. If no aberrant resultwas produced, the solution recorded in Parallel System Logs at S205 andProduction System Logs at S206 may be queued and/or promoted toproduction at S210.

If an aberrant result is produced as S209, however, the solution will beimmediately removed from the queue at S211. The promotion to productionevent will be queued at S212. As appropriate, the solution may beredeployed into Parallel System Request at S203, or completely preventedfrom being deployed in either a parallel or production environment atS213. In embodiments of the invention, redeployment may depend on theextent to which the aberrant result produced at S209 is impacting thesystem. It should also be noted that changes or solutions may bescheduled at S214 and entered into the production change queue at S215.Still further, any modifications to the system may be required to beassociated with a particular user account and/or user permissions inembodiments of the invention.

In this way, the system may immediately prevent any defect which wouldbe introduced or has been introduced due to parallel log monitoring ofexisting and new state systems. As existing defects are captured byautomatic defect resolution and resolved, these can be guaranteed not toimpact production any further, and thus the system drives out allproduction defects over a window of time, requiring less and lessmaintenance. If a new unknown defect is required to be resolvedmanually, the system automatically captures the resolution process andcan guarantee this defect resolution path is added to the repository ofresolutions it will use going forward. Interval based transactiontolerances prevent operation outside of mathematically provendemonstrable system limits.

FIG. 3 is a block diagram illustrating an operating environment inaccordance with an embodiment of the invention. In an embodiment of theinvention, automated defect resolution with interval analysis system 301a and parallel deployment with interval analysis system 301 b exist astwo subparts of a common system. Both automated defect resolution withinterval analysis system 301 a and parallel deployment with intervalanalysis system 301 b are connected over network 302 to financialinstitution systems 303. User accounts 304 a, 304 b . . . 304 n may beconnected over network 302 and provide access to financial institutionsystem 303 in conjunction with automated defect resolution with intervalanalysis system 301 a and parallel deployment with interval analysissystem 301 b. In embodiments of the invention, the user accounts 304 a,304 b . . . 304 n may be directly associated with automated defectresolution with interval analysis system 301 a and parallel deploymentwith interval analysis system 301 b. In embodiments of the invention,the user accounts 304 a, 304 b . . . 304 n may be directly associatedwith financial institution systems 303.

Financial institution systems 303 may include production system 305.Production system 305 may be any type of production system comprising aset of rules about behavior or otherwise known in the art. Inembodiments of the invention, the production system may be be associatedwith the financial institution.

In an embodiment of the invention, the user account holders 304 a, 304 b. . . 304 n may have accounts, such as, for example, accounts associatedwith a particular financial institution and generally managed by defectmanagement processing system 306, which may further be associated with adefect management database 307 for storing and retrieving dataassociated defect resolution. In embodiments of the invention, thisdefect management database 307 may be used in conjunction with any datarepositories associated with automated defect resolution with intervalanalysis system 301 a and/or parallel deployment with interval analysissystem 301 b. Additionally or alternatively, it may also be preferred tocombine some or all of the data stored in any data repositoriesassociated with automated defect resolution with interval analysissystem 301 a and/or parallel deployment with interval analysis system301 b with any data stored in defect management database 307.

In embodiments of the invention, defect management processing system 306may display a user interface over the network 302 which offers variousoptions to, and receives input from, the user account holders 304 a, 304b . . . 304 n who may manage or otherwise use the system. The useraccount holder 304 a, 304 b . . . 304 n may be individuals connectingover the network 302 to the defect management processing system 306and/or automated defect resolution with interval analysis system 301 aand parallel deployment with interval analysis system 301 b through theuse of computing devices such as desktop, laptop, portable computingdevices, or mobile devices, such as a smartphone or tablet device. Theuser accounts 304 a, 304 b . . . 304 n may be associated with one ormore administrative management accounts, which may themselves be furtherassociated with a specific or particular aspect of financial institutionsystems 303. The account management system 308 may be responsible forgenerating, maintaining and identifying user accounts andauthorizations, as well as associating user accounts with userpreferences. In embodiments of the invention, account management system308 may be linked directly with defect management processing system 306.

The defect management processing system 306 may further includeterminals or other equipment used to maintain and update recordsassociated with automated defect resolution with interval analysissystem 301 a and/or parallel deployment with interval analysis system301 b and/or financial institution systems 303. The defect managementprocessing system 306 may connect over network 302 for processing andsubsequent access by the user accounts 304 a, 304 b . . . 304 n. Thenetwork 302 is preferably the Internet, but may be or include othertypes of networks. The network 302 may include a wired or wireless localarea network (LAN) and a wide area network (WAN), wireless personal areanetwork (PAN) and other types or networks. When used in a LAN networkingenvironment, computers may be connected to the LAN through a networkinterface or adapter. When used in a WAN networking environment,computers typically include a modem of other communication mechanism.Modems may be internal or external, and may be connected to the systembus via the user-input interface, or other appropriate mechanism.Computers may be connected over the Internet, an Intranet, Extranet,Ethernet, or any other system that provides communications. Somesuitable communications protocols may include TCP/IP, UDP, or OSI forexample. For wireless communications, communications protocols mayinclude Bluetooth, Zigbee, IrDa or other suitable protocol. Furthermore,components of the system may communicate through a combination of wiredand/or wireless paths.

Account management database 308 may be or include any database thatstores data relating to the administrative accounts associated with aparticular user account 304 a, 304 b . . . 304 n. As set forth above,management database 308 may include administrative information and otherdata relevant to the user's account, but may also include other types ofdata as well; for instance, user privilege information and/or accessinformation, user organization information, whether there are multipleusers on a single account, information relating to past or recentactivity, etc.

FIG. 4 depicts a parallel deployment system 400 in accordance with anembodiment of the invention. Containing a modeling module 401, aproduction module 402, an interface module 403, a modeling repository404, and a production module 405, the parallel deployment system 400facilitates the creation and recording of parallel logs and productionlogs in accordance with embodiments of the invention.

The modeling module 401 facilitates the modeling, configuration andmanagement of solutions within a parallel system. The modeling module404 may generate the solutions against which interval-based transactiontolerances will be subsequently applied. In generating solutions withinmodeling module 401, the system for deploying a parallel deploymentsystem may operate by preventing any defects which would be (or couldbe) introduced in a production environment by parallel log monitoring ofexisting and new state systems. In an exemplary embodiment of theinvention, if an ATM receipt scan request is received by the automaticdefect resolution system, and the request fails due to limitedtablespace, the automatic defect resolution system may automaticallyexpand the tablespace and determine if it fixed the defect. If thedefect is fixed, the corresponding change is applied to the productionenvironment to avoid future similar defects. A log of record ofsolutions tested within modeling module 401 may be stored in modelingrepository 404.

The production module 402 of the parallel deployment system 400 may beconfigured to process solutions initially tested in the modeling module401 to improve solutions and store solutions in production repository405. In embodiments of the invention, the production module 402 may workin conjunction with modeling module 401 to generate results which may becompared using interval-based transaction tolerances as describedherein. Additionally or alternatively, the production module 402 mayexecute or promote solutions that have been successfully deployed bymodeling module 401. In an embodiment of the present invention, modelingmodule 401 contains a plurality of code modules, each of which, whenexecuted by a processor, transforms a solution generated and/or deployedby production module 402 into instructions storable at productionrepository 405 and further executable by a processor 406.

Upon the generation of one or more solutions, parallel deployment system400 may automatically interface, via interface module 403, with one ormore client systems in order to generate, for instance, records or logsof system activity.

FIG. 5 further depicts a working environment of the parallel deploymentsystem 500 in accordance with an embodiment of the present invention.Parallel deployment system 500 contains a modeling module 501,production module 502, an interface module 503, a modeling repository504, and a production module 505. Parallel deployment system 500 may beconnected to financial institution systems 520 and host system 530 vianetwork 510, each of which may be configured to deploy an automateddefect resolution system supported by an interval-based transactiontolerance engine as needed. In embodiments of the invention, paralleldeployment system 500 operates independently of financial institutionsystems 520 (the environment and systems which it administers). Whileembodiments of parallel deployment system 500 may be described as adistinct system that is independent from the financial institutionsystems 520 and/or host system 530, it should be appreciated that inother embodiments of the present invention, some or all of thecomponents of parallel deployment system 500, including its engines,modules and repositories, may be implemented as components contained inand operating at one or more unified systems.

As described above, embodiments of the system of the invention andvarious processes of embodiments are described. The system of theinvention or portions of the system of the invention may be in the formof a “processing machine,” i.e. a tangibly embodied machine, such as ageneral purpose computer or a special purpose computer, for example. Asused herein, the term “processing machine” is to be understood toinclude at least one processor that uses at least one memory. The atleast one memory stores a set of instructions. The instructions may beeither permanently or temporarily stored in the memory or memories ofthe processing machine. The processor executes the instructions that arestored in the memory or memories in order to process data. The set ofinstructions may include various instructions that perform a particulartask or tasks, such as any of the processing as described herein. Such aset of instructions for performing a particular task may becharacterized a program, software program, or simply software.

An noted above, the processing machine, which may be constituted, forexample, by the particular system and/or systems described above,executes the instructions that are stored in the memory or memories toprocess data. This processing of data may be in response to commands bya user or users of the processing machine, in response to previousprocessing, in response to a request by another processing machineand/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general purpose computer. However, the processing machinedescribed above may also utilize (or be in the form of) any of a widevariety of other technologies including a special purpose computer, acomputer system including a microcomputer, mini-computer or mainframefor example, a programmed microprocessor, a micro-controller, aperipheral integrated circuit element, a CSIC (Consumer SpecificIntegrated Circuit) or ASIC (Application Specific Integrated Circuit) orother integrated circuit a logic circuit, a digital signal processor, aprogrammable logic device such as a FPGA, PLD, PLA or PAL, or any otherdevice or arrangement of devices that is capable of implementing thesteps of the processes of the invention.

The processing machine used to implement the invention may utilize asuitable operating system. Thus, embodiments of the invention mayinclude a processing machine running the Microsoft WindowsTM VistaTMoperating system, the Microsoft WindowsTM XPTM operating system, theMicrosoft WindowsTM NTTM operating system, the WindowsTM 2000 operatingsystem, the Unix operating system, the Linux operating system, the Xenixoperating system, the IBM AIXTM operating system, the Hewlett-PackardUXTM operating system, the Novell NetwareTM operating system, the SunMicrosystems SolarisTM operating system, the OS/2TM operating system,the BeOSTM operating system, the Macintosh operating system, the Apacheoperating system, an OpenStepTM operating system or another operatingsystem or platform.

It is appreciated that in order to practice the method or the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing as described above is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, or any client server system thatprovides communication, for example. Such communications technologiesmay use any suitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions is used in the processing ofthe invention. The set of instructions may be in the form of a programor software. The software may be in the form of system software orapplication software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instructions or single programminglanguage be utilized in conjunction with the operation of the system andmethod of the invention. Rather, any number of different programminglanguages may be utilized as is necessary or desirable.

Also, the instructions and/or data used in the practice of the inventionmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software tor example, thatenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set orinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, a EPROM, a wire, a cable, a fiber,communications channel, a satellite transmissions or other remotetransmission, as well as any other medium or sourer of data that may beread by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, voice reader,voice recognizer, dialogue screen, menu box, list, checkbox, toggleswitch, a pushbutton or any other device that allows a user to receiveinformation regaining the operation of the processing machine as itprocesses a set of instructions and/or provide the processing machinewith information. Accordingly, the user interface is any device thatprovides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The use interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

It will be readily understood by those persons skilled in the art thatthe present invention is susceptible to broad utility and application.Many embodiments and adaptations of the present invention other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and foregoing description thereof, withoutdeparting from the substance or scope of the invention.

Accordingly, while the present invention has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentinvention and is made to provide an enabling disclosure of theinvention. Accordingly, the foregoing disclosure is not intended to beconstrued or to limit the present invention or otherwise to exclude anyother such embodiments, adaptations, variations, modifications andequivalent arrangements.

What is claimed is:
 1. A method for processing a request, the methodcomprising: receiving, by an interface, the request at a paralleldeployment system; duplicating, by a duplicator, the request into aparallel system request and a production system request; generating, bya processor, a parallel system log and a production system log;comparing, by the processor, transaction results for the request fromthe parallel system log and the production system log based on intervalbased transaction tolerances; determining, by the processor, whether anaberrant result is produced; and when the result is aberrant,determining an extent to which the aberrant result is impacting thesystem, and determining whether to promote the result to productionbased on the determined impact extent.
 2. The method of claim 1, furthercomprising initially dividing the request via the duplicator.
 3. Themethod of claim 1, further comprising detecting a defect upon processingof the request.
 4. The method of claim 3, further comprising attemptingautomatic issue resolution for the detected defect by detectingcorrespondence to known defects.
 5. The method of claim 4, furthercomprising continuing request processing upon successful automatic issueresolution.
 6. The method of claim 4, further comprising performing anautomated fix from a defect repository when no known defects arematched.
 7. The method of claim 6, further comprising determiningwhether the automated fix causes a tolerance issue through deployment ofthe interval based transaction tolerances.
 8. The method of claim 7,further comprising closing the defect as resolved when no toleranceissue is created and continuing to process the request.
 9. The method ofclaim 7, further comprising creating a record for a manual fix of thedefect when the automated fix creates a tolerance issue.
 10. The methodof claim 9, further comprising utilizing the created record for futureautomated issue resolution.
 11. A parallel deployment system forprocessing a request, the system comprising: an interface receiving therequest at a parallel deployment system; a duplicator duplicating therequest into a parallel system request and a production system request;and a processor processing the requests and generating a parallel systemlog and a production system log, the processor executing instructionsfor: comparing transaction results for the request from the parallelsystem log and the production system log based on interval basedtransaction tolerances; determining whether an aberrant result isproduced; and when the result is aberrant, determining an extent towhich the aberrant result is impacting the system, and determiningwhether to promote the result to production based on the determinedimpact extent.
 12. The system of claim 11, further comprising anautomated defect resolution system.
 13. The system of claim 12, whereinthe automated defect resolution system determines if a defect preventsprocessing of the request.
 14. The system of claim 13, wherein theautomated defect resolution system attempts automatic defect resolutionfor the detected defect by detecting correspondence to known defects.15. The system of claim 14, wherein the automated defect resolutionsystem authorizes continuing request processing upon successfulautomatic defect resolution.
 16. The system of claim 14, wherein theautomated defect resolution system performs an automated fix from adefect repository when no known defects are matched.
 17. The system ofclaim 16, wherein the automated defect resolution system determineswhether the automated fix causes a tolerance issue through deployment ofthe interval based transaction tolerances.
 18. The system of claim 17,wherein the automated defect resolution system closes the defect asresolved when no tolerance issue is created and continuing to processthe request.
 19. The system of claim 17, wherein the automated defectresolution system creates a record for a manual fix of the defect whenthe automated fix creates a tolerance issue.
 20. The system of claim 19,wherein the created record is utilized for future automated issueresolution.